We use our own mime type to support being asked for different version of a resource by the clients. By sending in an accept header with the correct mimetype, say "application/vnd.eve.ccp.Tournament-v1" the server knows to return you that particular version. It allows us to release new versions of these resource and your client will keep working as long as we support the version you want.

"{
"message": "The route /tournaments/2/series/0 was not found, did you forget the trailing slash?",
"key": "routeMissing",
"exceptionType": "NotFoundError"
}"

Need to renew your domain registration dude ;)

(also, get isk value up on the destroyed ships, that was a >9bil flagship that died in the first match~)

{
"message": "The route was not found",
"key": "routeMissing",
"exceptionType": "NotFoundError"
}

There are *significant* hurdles in the way of applying this technology to Eve in general. The tournament provides us a very bounded environment - 15 minutes max, 24 ships max, constrained location - which makes this sort of thing possible.

Well, that's partially the magic of Eve. The actual clients don't get x,y,z except when they or someone else joins a bubble. A part from that, they only get the "Dude X started orbiting Dude Y" or "Dude A started shooting dude B" events and the simulation is then synchronized. If no one clicks anything, even a 2000 man fleet fight produces just about no traffic.

The method we use here needs to store all x,y,z and send them down all the time, no local simulation. THAT doesn't scale well to 2000 ship fleet.